-
Notifications
You must be signed in to change notification settings - Fork 705
[WIP] Map issue template metadata to NewIssue.md #8263
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Co-authored-by: alexr00 <38270282+alexr00@users.noreply.github.com>
Co-authored-by: alexr00 <38270282+alexr00@users.noreply.github.com>
alexr00
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@copilot The issue template is yml, which means we end up with extra yml characters like this:
Assignees: @- alexr000
Labels: ["bug", "triage"]
Co-authored-by: alexr00 <38270282+alexr00@users.noreply.github.com>
Fixed in 394a879. The |
Plan: Map metadata from issue templates to NewIssue.md
Understand current implementation
getDataFromTemplateIssueTemplateinterface inutil.tsNewIssueFileOptionsinterface inissueFile.tsmakeNewIssueFilemethod inissueFeatureRegistrar.tscreateIssuemethodImplement changes to support labels and assignees in templates
IssueTemplateinterface to includelabelsandassigneesgetDataFromTemplatemethod to parselabelsandassigneesfrom YAML frontmatterNewIssueFileOptionsinterface to includelabelscreateIssuemethod to pass template labels and assignees to optionsmakeNewIssueFilemethod to populate labels line with template labelschooseTemplatereturn type to useIssueTemplateparseYamlTemplateto extract labels and assignees from YAML templatesTest the changes
Run code review and security checks
Security Summary
No security vulnerabilities were discovered during the CodeQL security scan.
Original prompt
💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.